Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

blog: registration: Post on registration management #734

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

rkdarst
Copy link
Member

@rkdarst rkdarst commented Dec 5, 2022

  • History of registration, difficulties of doing it with teams, why
    this appears online but not in-preson, distributed registration as a
    strategy.
  • It does not include our latest practices and what we raret trying
    to do in the future - others can fill that in.
  • Please add yourself to authors when you add more.

- History of registration, difficulties of doing it with teams, why
  this appears online but not in-preson, distributed registration as a
  strategy.
- It does *not* include our latest practices and what we raret trying
  to do in the future - others can fill that in.
- Please add yourself to authors when you add more.
@rkdarst rkdarst force-pushed the rkdarst/registration branch from 349c1c9 to 271d8bf Compare December 5, 2022 13:47
@rkdarst
Copy link
Member Author

rkdarst commented Dec 5, 2022

@MatiasJJ @bast, there are places for you to fill out here (or let me know the general idea and I can write), I think you know the current best practices / problems better than me. Remember to add yourself as an author if you modify!

@bast
Copy link
Member

bast commented Dec 5, 2022

Thanks a lot. I will carefully read and comment since this is a problem I am thinking about a lot these days and also we discussed this earlier today in meeting.

@rkdarst rkdarst marked this pull request as draft December 8, 2022 13:09
@bast
Copy link
Member

bast commented Dec 11, 2022

I will work on registration coming week and then this will nicely fit into my work.

@bast
Copy link
Member

bast commented Dec 16, 2022

Finally reviewing ...

@bast
Copy link
Member

bast commented Dec 16, 2022

Points to possibly add/expand:

  1. No-shows are a problem in any event but it is an extra problem in our team-based setup where we try to form teams and match teams to exercise leads. It is a problem then if either most of the team does not show up (this has happened frequently) or the exercise lead does not show up (this hasn't happened much). The fact that some exercise leads felt "unused" is for me the major problem to fix in upcoming events.

  2. Problem with distributed registration: this may be clear to all organizers but not clear to the learners. Especially if all registrations don't open at the same time, the motivated learner may register in the "wrong" one which can lead to confusion in communication and team formation and show-up-expectations.

@rkdarst
Copy link
Member Author

rkdarst commented Dec 16, 2022

(2) is a good point! distributed registration makes things easier. but then multiple-registrations means there will be no-show in one or the other, making more work.
Will update with this.

@bast
Copy link
Member

bast commented Mar 7, 2023

I would like this to not get lost but also we have moved on a bit. Will it help if we meet for a 45 min call and finish this live together and get it published?

@bast
Copy link
Member

bast commented May 19, 2023

I am sorry we never got this merged but maybe we can update it with lessons learned from March workshop and plan for the September and future workshops?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants